Confirming compliance with a configuration

ABSTRACT

Confirming compliance with a configuration includes: receiving information about a fixture, where the information includes a specified configuration of items to be displayed on the fixture; generating a display using the information, where the display depicts the specified configuration; presenting the display using a graphics system of a computing device; receiving an image depicting an actual configuration of the fixture; associating metadata with the image, where the metadata includes searchable data that distinguishes the fixture from at least some other fixtures of like type; sending the image, along with the metadata, over a network to a server that is remote from the computing device; and in a case that the specified configuration substantially matches the actual configuration, sending, along with the image and the metadata, a message indicating that the fixture is in compliance with the specified configuration.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application claims priority to U.S. Provisional ApplicationNo. 61/492,243, filed on Jun. 1, 2011, the contents of which are herebyincorporated by reference into this patent application as if set forthherein in full.

TECHNICAL FIELD

This patent application relates generally to confirming that a retailmerchandising fixture or other structure is in compliance with aspecified configuration.

BACKGROUND

Distributors provide products to retailers for sale. Typically, adistributor will provide a number of the latest products to theretailer. The products are often provided without regard to the needs ofthe consumer. As a result, some of those products are sold by theretailer, and some are not. The surplus that is not sold generallycannot be sent back to the distributor. As a result, the retailer willtypically put the surplus “on sale”, often at a loss.

Product placement can be key in determining whether a product is sold atthe retail level or whether the product remains unsold. A manufacturermay provide guidelines as to how its products are to be displayed. Theseguidelines may be a result of time and effort spent to determine how toachieve optimal, or at least enhanced, sales based on product placement.However, these guidelines are subject to interpretation by the retailerand local store. As a result, the actual product display at a retaillocation may deviate considerably from the one intended either by themanufacturer or the retailer. The manufacturer or the retailer may beunable to enforce compliance with their guidelines among retail outletswithout policing the retail outlets in person. This can be impractical,particularly where there are a large number of retail outlets.

SUMMARY

This patent application describes methods and apparatus, includingcomputer program products, for confirming that a fixture or otherstructure is in compliance with a specified configuration.

An example of the foregoing methods and apparatus includes: receivinginformation about a fixture, where the information corresponds to aconfiguration of items to be displayed on the fixture; generating adisplay using the information, where the display depicts theconfiguration; presenting the display using a graphics system of acomputing device; receiving an image depicting an actual configurationof the fixture; associating metadata with the image, where the metadatacomprises searchable data that distinguishes the fixture from at leastsome other fixtures of like type; sending the image, along with themetadata, over a network to a server that is remote from the computingdevice; and, in a case that the configuration substantially matches theactual configuration, sending, along with the image and the metadata, amessage indicating that the fixture is in compliance with theconfiguration. The method and apparatus may include one or more of thefollowing features, either alone or in combination.

The information may comprise a floorplan of a location that includes thefixture. The display may comprise a first display and a second display.The first display may be an image of the floorplan and may comprise anicon corresponding to the fixture. The second display may depict thefloorplan and may be presented in response to selection of the icon onthe first display. The server may be a first server, and the informationmay be received from a second server that is different from the firstserver. The metadata may be received from the second server. Theconfiguration may substantially match the actual configuration if itemsand locations of items on the actual configuration match, to within apercentage, items and locations of items on the configuration. A processmay be performed that includes determining that the configurationsubstantially matches the actual configuration. The determining may beperformed by comparing the configuration to the actual configuration.The comparing may be performed manually. The comparing may be performedautomatically by identifying items in the image depicting the actualconfiguration using one or more image matching processes, and bycomparing attributes of the identified items to attributes of items inthe configuration. In a case that the configuration does notsubstantially match the actual configuration, a message may be sent, tothe server, indicating that the fixture is not in compliance with theconfiguration. The metatdata may comprise data identifying at least oneof the following: a type of the fixture, items on the fixture, and alocation of the fixture.

Any two or more of the features described in this patent application,including in this summary section, may be combined to form embodimentsnot specifically described in this patent application.

All or part of the systems and techniques described herein may beimplemented as a computer program product that includes instructionsthat are stored on one or more non-transitory machine-readable storagemedia, and that are executable on one or more processing devices.Examples of non-transitory machine-readable storage media include e.g.,read-only memory, an optical disk drive, memory disk drive, randomaccess memory, and the like. All or part of the systems and techniquesdescribed herein may be implemented as an apparatus, method, orelectronic system that may include one or more processing devices andmemory to store executable instructions to implement the statedfunctions.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features,objects, and advantages will be apparent from the description anddrawings, and from the claims.

DESCRIPTION OF THE DRAWINGS

FIGS. 1 to 3 are block diagrams depicting, conceptually, the processesdescribed herein for retrieving a specified configuration of a fixture,comparing the specified configuration to an actual configuration of thefixture, and reporting compliance, or lack thereof, of the fixture withthe specified configuration.

FIG. 4 is a block diagram of a network system on which the processesdepicted conceptually in FIGS. 1 to 3 may be implemented.

FIG. 5 is a flowchart showing an example of the processes depicted inFIGS. 1 to 3.

FIG. 6 is an example of an actual configuration of a fixture and of auser comparing a specified configuration of the fixture to the actualconfiguration.

FIG. 7 is an example of an image of an actual configuration of afixture.

FIG. 8 is a user interface (UI) showing a floorplan and fixture icons.

FIG. 9 is a UI showing an image of an actual configuration of a fixturethat was included in the floorplan of FIG. 8.

Like reference numerals in different figures indicate like elements.

DETAILED DESCRIPTION

Described herein is a system for reporting that a fixture or otherstructure complies with specified requirements of an entity, such as amanufacturer. The system may be performed by one or more processingdevices of a computing device, and may include receiving informationabout the fixture, such as a specified configuration of items to bedisplayed on the fixture. The system may also include generating adisplay that depicts the specified configuration using the information,presenting the display using a graphics system of the computing device,receiving an image depicting an actual configuration of the fixture, andassociating metadata with the image. The metadata may include searchabledata that distinguishes the fixture from at least some other fixtures oflike type (e.g., identical fixtures that are configured differently,different fixtures that are configured identically, identical fixturesthat are configured identically, etc.). The system may also includesending the image, along with the metadata, over a network to acompliance server that is remote from the computing device. The metadatamakes images of the actual configurations searchable, e.g., by an entitythat set the specified configuration. If the specified configurationsubstantially matches the actual configuration, the system also includessending, along with the image and the metadata, a message indicatingthat the fixture is in compliance with the specified configuration.FIGS. 1 to 3, below, depict the above system conceptually.

In FIGS. 1 to 3, the cellular telephone industry is used to describe howthe above system works. In this example, the products are cellulartelephones and accessories, and the retail locations are stores, such asthose for Verizon® and AT&T®.

Referring to FIG. 1, an example of the foregoing system may beimplemented, in part, on a computing device 10. In this example, mobilecomputing device 10 is a tablet computer that includes an outward-facingcamera. However, other types of computing devices may be used in lieuof, or in addition to, a tablet computer. In FIG. 1, fixture 12, whichmay be, e.g., a kiosk or a display wall, is located at a retail store.Fixture 12 displays items which, in this example, include accessoriesfor use with cellular telephones, such as headsets, chargers, cases, andthe like. Fixture 12 is configured to display these items in a mannerdesigned to enhance sales, as described in more detail below. To thisend, a specified configuration for the fixture is stored, e.g., in aserver (not shown in FIG. 1) that is accessible to computing device 10over a network. The specified configuration may be associated with asales promotion or the like designed to promote sales of a particularitem or items in general. The specified configuration may be predefinedin that it is a direct representation, in the system, of theconfiguration of the fixture. Alternatively, data may be stored in thesystem that may be used to calculate or otherwise determine thespecified configuration of the fixture. In this case, the data that isstored need not be a direct representation, in the system, of theconfiguration of the fixture. Accordingly, in the context of thisapplication, references to storage of the specified configuration mayrefer to storage of data representing the specified configuration ofstorage of data used to generate a representation of the specifiedconfiguration.

The specified configuration may be stored in association with afloorplan 14 for a store where fixture 12 is located. Floorplan 14 maybe a block diagram, as shown, having a shape that roughly represents tothe shape of the corresponding store. Floorplan 14 may have metadataassociated therewith, which identifies the floorplan as being for thestore, and which specifies various other characteristics of the store,e.g., the location of the store, the identity of the store, the managerof the store, and the like. In this example, floorplan 14 includes icons16 a to 16 c that represent fixtures in the store. The icons 16 a to 16c are located at about the same location as fixtures in the store. Theicons 16 a to 16 c may include associated hyperlinks that, whenselected, display the specified (and, if available) currentconfiguration of each corresponding fixture. In a tablet computer orother touch-screen system, a fixture icon may be selected by touchingthe icon.

In the example of FIG. 1, icon 16 c corresponds to fixture 12, asindicated by arrow 18. Icon 16 c provides access to a specified (e.g.,retailer or manufacturer-specified) configuration for fixture 12. Thespecified configuration may include metadata 20 associated therewith, asindicated by arrow 22. Metadata 22 may be information about, e.g., thetypes and locations of items (e.g. products) included on the specifiedconfiguration fixture 12. The metadata associated with floorplan 14 maybe part of metadata 20, and may also be associated with each fixtureicon 16 a to 16 c (and, thus, with each specified fixtureconfiguration).

In this example, a user 24 of computing device 10 accesses floorplan 14via a secure Web site. User 24 selects icon 16 c to display thespecified configuration 26 of fixture 12 via the graphics system,including the display screen 28, of computing device 10. This is shownin FIG. 2. The actual configuration of fixture 12 is compared to thespecified configuration 26 displayed on computing device 10. In theexample of FIG. 2, the comparison is performed manually. That is, user24 visually compares the specified configuration 26 to the actualconfiguration 12. In an alternative implementation, the comparison maybe performed automatically using, e.g., image recognition code executingon computing device 10 or elsewhere on a network connected to thecomputing device (e.g., in a cloud computing context, this functionalitywould be implemented in “the cloud”). For example, user 24 may take apicture of fixture 12 using, e.g., an outward-facing camera 30 includedon computing device 10. Appropriate image recognition code, inconjunction with information available on a network, such as theInternet, may be used to identify the items displayed on fixture 12,along with their locations. This information may be compared to themetadata 20 associated with the specified configuration in order todetermine if the actual configuration matches the specifiedconfiguration.

In any case, if the actual configuration of fixture 12 is identical, orsubstantially similar, to the specified configuration, fixture 12 isdeemed to be in compliance with the specified configuration. In thiscontext, “substantially similar” may indicate that a certain percentageof items in the specified configuration are in the actual configurationand/or that a certain percentage of items in the actual configurationare at the locations in the fixture specified by the specifiedconfiguration.

Following comparison, user 24 may take a picture of the actualconfiguration of fixture 12 using the camera on computing device 10(assuming that a picture has not already been taken). The resultingimage may be associated with metadata for the specified configuration,and the combination sent to compliance server 32 (FIG. 3). If it hasbeen determined that the actual configuration is compliant, then theimage may be sent along with a message indicating that the actualconfiguration is in compliance. If it has been determined that theactual configuration is not in compliance, then the image may be sentalong with a message indicating that the actual configuration is not incompliance. If available, the message may specify what, in the actualconfiguration, deviates from the specified configuration. In eithercase, the message may include appropriate metadata that is indicative ofcompliance or non-compliance, and that may be stored with the image.

The foregoing process is depicted conceptually in FIG. 3. Specifically,FIG. 3 shows computing device 10 taking a picture 34 (“fixture image”)of the actual configuration of fixture 12, and sending the resultingimage to compliance server 32. As shown in FIG. 3, metadata, such asmetadata 20 or other metadata described herein, is associated with image34. The metadata may be associated with image 34 by computing device 10.For example, computing device 10 may download the metadata and appendthe metadata to image 34 prior to sending image 34 to compliance server32. Alternatively, computing device 10 may instruct a server (not shown)containing the metadata for a particular fixture to send that metadatato compliance server 32, along with a fixture-specific identifier.Computing device 10 may append that same identifier to image 34.Compliance server 32 may then associate image 34 with the appropriatemetadata using the identifier. An advantage of this configuration isthat it reduces the amount of processing required by computing device10.

User 24 interacts with computing device 10 through a user interface (UI)that is generated by code that controls and/or implements the processesof FIGS. 1 to 3. The UI may include one or more fields that accept userinput (e.g., a “comments” field). The user input may include anyinformation, such as information about the store, the user, the fixture,and the like. This user-input information may be stored as metadata tobe associated with an image of the fixture, e.g., with an image of theactual configuration taken by the camera.

Compliance server 32 stores the image of the actual configuration of thefixture in a database 38 in association with the metadata for thespecified configuration. Compliance server 32 also stores, inassociation with the image, any other metadata, such as the time thatthe image has been created and any user-input information. Pointers,tables, and/or other virtual structures, may be used to make theappropriate associations.

The metadata for each image may be specific to that image, and thereforemay distinguish the image from other fixture images in the database. Thedatabase is searchable using the metadata. For example, an entity thatdesigned the specified configuration (e.g., a manufacturer of productsor associated accessories) may search database 38 in order to identifyan image showing the actual configuration of a fixture in order toconfirm that the actual configuration of the fixture complies with therequirements of the specified configuration. A manufacturer or otherentity wanting access to the compliance server's information, maymaintain an account with the proprietor of compliance server 32, andaccess that account via a Web page hosted by compliance server 32.

Database 38 may be part of, or otherwise accessible to, complianceserver 32. Database 38 may store images of fixtures, along with theassociated metadata described herein. The associated metadata mayinclude, but is not limited to, information about cellular telephonesand their accessories in a fixture, attributes of a retail storeassociated with the fixture, locations of items on the fixture, a timeat which an image was taken, and other information. Examples ofinformation that may be included in the metadata are provided below. Itis noted that an image need not have associated with it all of theinformation described below, and that this information is presentedsimply to give examples of the types of information that may beassociated with an image of a fixture.

Information about a cellular telephone may include any information thatidentifies the cellular telephone. For example, the information mayinclude the maker of the cellular telephone (e.g., Samsung®, Nokia®,Apple®, etc.), the model name of the cellular telephone (e.g., iPhone®,chocolate phone, Razr, etc.), the model number of the cellular telephone(e.g., SKU—stock keeping unit—number), and the type of cellulartelephone (e.g., smart phone, go-phone, 3G phone). There is no limit onthe amount and type of information that may be associated with an image.For example, the database may also include the colors of the cellulartelephones, their cellular carriers (e.g., AT&T®, Verizon®, etc.) theirprimary and/or secondary functionalities (e.g., plays music), theirsizes, the communication schemes that they employ (e.g., CDMA or GSM),and their ability to operate outside the United States.

Information about cellular telephone accessories may include anyinformation that identifies accessories for use with cellulartelephones. The information stored in database 38 may relate toaccessories for cellular telephones that are not described in thedatabase, but that nevertheless may be displayed. As was the case withthe information about cellular telephones, the information about theaccessories may include the maker of the accessories (e.g., Samsung®,Nokia®, Apple®, etc.), the type of the accessory (e.g., Bluetooth®earpieces, headphones, cases, batteries, chargers, car chargers, etc.),the model number (e.g., SKU number) of each accessory, and theidentities of cellular telephones with which each accessory will work.There is no limit on the amount and type of information aboutaccessories that may be associated with an image. For example, thedatabase may also include the colors of the accessories, cellularcarriers (e.g., AT&T®, Verizon®, etc.) associated with the accessories,their functionalities, their sizes, and the like.

Attributes of retail stores may include any information that identifiescharacteristics of a retail store at which cellular telephones and/oraccessories therefor are sold. In this regard, each retail store mayhave a profile, which may be stored in database 38, and which containsthe attributes associated with that retail store. The attributes mayinclude the geographic location of the store (e.g., country, city,state, neighborhood, street address), the capacity of the store to sellproduct (e.g., capacity to display 50 cellular telephones and 150corresponding accessories), the demographics of people who frequent thestore (e.g., college students, young professionals, senior citizens),and the layout of the store, such as the positioning (relative orabsolute) of display areas for cellular telephones and accessoriesvis-à-vis other features of the store, such as a checkout area orservice desk. There is no limit on the amount and type of attributesthat may be associated with an image. For example, the attributes mayalso identify the physical size of the store, other types of products(e.g., non-cellular-related) that are sold by the store, the rate ofinventory turn-over of the store, the sales volume of the store, abreak-down of sales by cellular telephone, accessory, or other product,and any other attributes that further characterize the store.

Information about the layout of the fixture may include a uniqueidentifier for the fixture. The unique identifier for the fixture may beunique among all fixtures in the database, or it may be unique amongfixtures at the subject retail location. Alternatively, two (or more)identifiers such as these may be associated with each fixture. Theinformation about the layout may also identify which products arelocated at particular locations on the fixture (along with theirassociated metadata described above), possible alternatives forparticular products, times periods during which those products are to bedisplayed, and the like. Basically, any appropriate information may beincluded in the metadata.

As noted above, a fixture may be configured to display items in a mannerdesigned to enhance sales of those items. To this end, the specifiedconfiguration may be designed in accordance with one or more rules forselecting and arranging cellular telephones and their accessories infixtures in retail stores, templates of fixtures (e.g., kiosks ordisplay walls) within the retail stores, and filters that may limit (or,in some cases, expand) layout of products within one or more retailstores. Code for designing the specified configuration may be executedby the same server(s), site(s), or entity(ies) that provide thefloorplans and metadata described above (e.g., floorplan 14 in FIG. 1).An example of such a server is server 40 of FIG. 4, which is describedbelow.

In the cellular telephone example, rules are used for selecting andarranging cellular telephones and their accessories on fixtures in aretail store. The rules may be fixture-specific, meaning that theypertain to a particular fixture or type of display fixture, or they maybe generic and simply applied to a particular fixture, type of displayfixture, or the store in general. For example, rules may state that aparticular type of cellular telephone is to be located at a particularlocation on a fixture (e.g., iPhones® always must be located on the farright of a fixture), that there must be no more than a particular numberof cellular telephones on a fixture (e.g., a fixture must not containmore than five LG® chocolate phones), that the fixture may not containtwo types of cellular telephones from the same manufacturer, thataccessories for a particular manufacturer must be proximate (e.g.,below) a particular cellular telephone from that same manufacturer, andthat only accessories used with a particular cellular telephone may bedisplayed proximate (e.g., below) that cellular telephone. Rules mayalso specify, e.g., that a particular brand or type of cellulartelephone is to be given priority over other cellular telephones in agroup (e.g., the priority cellular telephone is to be given the bestdisplay position on a fixture), that particular types, colors or brandsof cellular telephones are to be grouped for display, and thatsub-groups of cellular telephones within a group are to have specificdisplay characteristics. Layouts may then be limited/dictated by thisinformation, regardless of fixture. There is no limit on the amount andtype of rules that may be included in the database. Rules may be added,deleted or modified.

Rules for arranging cellular telephone accessories may be similar tothose for arranging cellular telephones. The rules for arrangingaccessories may also specify spatial relationships of accessories tocorresponding cellular telephones. For example, a rule may specify thata certain number of iPhone® accessories (e.g., two) must be placeddirectly below a corresponding iPhone® on a fixture. Another rule mayspecify what those accessories must be, e.g., a case, a Bluetooth®headset, etc. Another rule may specify who the manufacturers of thoseaccessories must be, e.g., only Belkin® accessories. As was the casewith cellular telephone rules, there is no limit on the amount and typeof rules that may be included in the database. Rules may be added,deleted or modified.

The server that stores the rules may also include a database. Thedatabase may store templates for fixtures within retail stores. Thetemplates contain placeholders, which specify where, on the fixture,cellular telephone(s) and/or accessory(ies) may be placed. The templatesare, essentially, physical layouts of display areas of correspondingfixtures, with placeholders substituted for actual products, herecellular telephones and their accessories. In an example, a template isstored for every type of fixture used in a retail stores identified inthe database. Each template may contain metadata that associates it withone or more of those retail stores. Templates may also be stored forportions of fixtures, thereby allowing the system to dictate display ononly that portion of a fixture, leaving the remainder of the fixture'sdisplay to the retail owner's discretion.

The same server(s) that stores rules and template may also storesfilters that may place further restrictions on product distribution andplacement. For example, the filters may take into account retail storeattributes and cellular telephone and accessory information to determine(e.g., limit or expand) which cellular telephones and accessories can bedisplayed in a particular retail store. For example, currently, WestVirginia does not have 3G network coverage. Accordingly, a server maycontain a filter that limits retail stores located in West Virginia tonon-3G cellular telephones. Another filter might require that retailstores in areas populated predominantly by students receive cellulartelephones that have entertainment features, e.g., that are capable ofplaying music, or not receive primarily business-oriented cellulartelephones. Another filter might require that retail stores inlow-income areas receive lower-cost cellular telephones or not receivecellular telephones whose cost is above a certain level. Another filtermight require that retail stores in areas frequented by businesspeoplereceive a higher proportion of Blackberry® phones and their accessories.Another filter might require that stores in Massachusetts should receivea particular type of phone, such as an iPhone®. There is no limit on theamount and type of filters that may be included in the database. Filtersmay be added, deleted or modified.

Filters may also be specified for accessories. In an example, thefilters refer to attributes of locations or lists of locations. Forexample, a filter might identify a town as a university town. Anotherfilter might require that a higher percentage of car chargers be sent tostores located in Los Angeles than to stores located in Boston. As wasthe case above, there is no limit on the amount and type of filters thatmay be included in the database. Filters may be added, deleted ormodified.

FIG. 4 is a block diagram of an example of a system 42 on which theprocesses of FIGS. 1 to 3 may be implemented. System 42 includes one ormore computing devices, one or more servers, and a network 44, overwhich the elements of FIG. 4. may interact. Also shown in FIG. 4 arecomputer systems, which may be maintained by manufacturers or otherentities that have accounts with a compliance server 32.

A computing device 46 may be, or include, a mobile computing device suchas a tablet computer having an outward-facing camera or other imagecapture system. In this context, “outward-facing” refers to a camera onthe back of, or non-display side of, the computing device. However,computing device 46 is not limited to a tablet computer, but rather mayinclude other types of computing devices, such as a cellular telephone(e.g., a feature phone or a smartphone), a desktop computer, a laptopcomputer, a handheld computer, a network appliance, a camera, anenhanced general packet radio service (EGPRS) mobile phone, a mediaplayer, a navigation device, an electronic mail (e-mail) device, a gameconsole, an electronic reader, or a combination of any two or more ofthese data processing devices or other data processing devices. Thecomputing device has a built-in camera that is outward facing; however,that is not a requirement. Instead, the computing device may have anyway of connecting to, or receiving images from, a device capable oftaking a picture of a fixture. In this context, “images” includes allappropriate types of still image or video. Computing device 46 may bethe same as computing device 10 of FIGS. 1 to 3.

Computing device 46 includes one or more processing devices 48, memory50 and a storage system 52. Storage system 52 can store an operatingsystem (OS) 54, and a Web browser 56, such as GOOGLE CHROME™ orMICROSOFT INTERNET EXPLORER®, for accessing servers 32 and 40. Storagesystem 52 can also store computer code 52, such as an application. Theapplication may be for performing at least some of the functionsdescribed with respect to FIGS. 1 to 3 and 5 (below), or for interactingwith a remote application capable of performing at least some of thosefunctions.

Each server can represent various forms of servers, such as a Webserver, an application server, a proxy server, a network server, or aserver farm. Each server can also include, or be associated with, one ormore data repositories (not shown separately) for storing informationregarding fixtures, their configurations, metadata, rules and filtersfor configuring fixtures, and any code for performing the processesdescribed herein.

In this example, server 32 corresponds to the compliance server of FIGS.1 to 3. Server 32 includes database 38 for storing images 60 of fixturesand associated metadata 62 provided, e.g., by computing device 46 andothers like it. Server 32 also stores Web server code 64, through whichthis information may be accessible, via network 44, to other entities,such as computer systems 66 to 68. In this example server 40 storesinformation for floorplans 70, information for fixtures 72, and metadata74 including information about, among other things, the specifiedconfigurations of the fixtures. Server 40 also stores a Web server 76that makes this information accessible to entities on network 44 using,e.g., Web services. Server 40 may also store executable code toimplement at least some of the functionality described with respect toFIGS. 1 to 3 and 5. In this regard, in an example, that functionalitymay be implemented via a Web-based application executed by server 40, orthat functionality may be implemented via computer code executing oncomputing device 46. In any case, there may be an interaction betweencode on computing device 46 and code on server 40 in order to implementsome or all of the functionality described herein. Server 40 may alsostore the rules, filters and templates 78 described above.

Each server can include one or more processing devices, memory and astorage system, which may be similar to that depicted in FIG. 4 forcomputing device 46. The storage system can include an operating system(OS) and a Web server program, such as those described above. Thestorage system may include a repository that stores a database withinformation appropriate for that server.

Network 44 can represent one or more communications networks that canallow devices (e.g., the computing devices and servers of FIGS. 1 to 4)to effect wired or wireless communication through a communicationinterface (not shown), which may include digital signal processingcircuitry, where necessary. Network 44 can include one or more networksavailable for use by the computing devices, including location areanetworks (LANs) and the Internet. The network(s) may provide forcommunications under various modes or protocols, such as InternetProtocol (IP), Global System for Mobile communication (GSM) voice calls,Short Message Service (SMS), Enhanced Messaging Service (EMS),Multimedia Messaging Service (MMS) messaging, Code Division MultipleAccess (CDMA), Time Division Multiple Access (TDMA), Personal DigitalCellular (PDC), Wideband Code Division Multiple Access (WCDMA),CDMA2000®, or General Packet Radio System (GPRS), among others. In anexample, network communication may occur through a radio-frequencytransceiver. In addition, short-range communication may occur, such asusing a Bluetooth®, Wi-Fi®, or other such transceiver.

Computer systems 66 to 68 may include any appropriate type of computersystem that is capable of accessing compliance server over network 44.For example, computer systems 66 to 68 may be the same as, or similarto, computer system 46. Computer systems 66 to 68 may also include oneor more servers, which may be similar in structure to servers 32 and 40,and one or more mainframe computers (not shown) that provide networkaccess.

FIG. 5 is a flowchart showing an example of a process 80 for reportingcompliance of a fixture with a specified configuration set, e.g., by anowner of the fixture. Process 80 may be an implementation of theprocesses depicted graphically in FIGS. 1 to 3. Referring also to FIG.4, in this example, process 80 is performed by code executing oncomputing device 46. As noted, however, in other implementations, atleast part of process 80 may be performed by code executing on server 40or on other device(s) in network or direct communication with computingdevice 46.

Process 80 receives (82) information relating to a fixture. In thisexample, the information includes a floorplan showing a layout of aretail location containing the fixture. The floorplan includes one ormore selectable icons, at least one of which corresponds to a fixture ofinterest in the floorplan. Information is associated with this icon. Theinformation, in this example, includes a specified configuration ofitems to be displayed on the fixture. The specified configuration may beset by an owner of the fixture or by a manufacturer of items on thefixture, and may be generated, e.g., on server 40, in accordance withone or more rules that are written to enhance sales of items on thefixture. As noted, the specified configuration may specify which itemsare to be included on the fixture and an arrangement of those items onthe fixture. The specified configuration may also include associatedmetadata, e.g., of the type described herein. For example, the metadatamay include information about fixtures that are displayed in thespecified configuration.

Process 80 generates (84) a display using the information. The displayincludes data defining an image of the floorplan, along with iconscorresponding to fixtures. In this example, the display is presented(86) using a graphics system of computing device 46. For example, thedisplay may be presented on a liquid crystal (LCD) display or any othertype of display available on a tablet computer.

One of the icons on the display may be selected to display the specifiedconfiguration of the corresponding fixture. The specified configurationmay include images of items that are supposed to be included on thefixture. The data may specify block diagram form with labels for items,or the data may specify computer-generated graphic(s) of the fixture anditems, with written labels, if appropriate. Process 80 presents (86)(e.g., renders) the display to depict the fixture in its specifiedconfiguration. The specified configuration of the fixture displayed onthe computing device may be compared to the actual configuration of thecomputing device (12 in FIG. 1).

More specifically, as described above, a user may visually compare thespecified configuration of the display to the actual configuration, andmake a mental determination as to whether the two match or are similarenough that the actual configuration is acceptable (e.g., a certainnumber of items are in the correct location on the fixture, even thoughothers are not). This is depicted in FIG. 6, in which a user 90 comparesan actual configuration of a fixture 92 to a specified configuration 94displayed on a computing device 96. In other implementations, imagerecognition code, which may run on computing device 46 or server 40, maybe implemented to recognize the fixture and the items displayed thereonin the actual configuration. A computer-generated match may be achievedby comparing metadata of the identified images to metadata associatedwith the specified configuration.

In any case, after it is determined whether the specified configurationand the actual configuration match, or are similar enough that theactual configuration is acceptable, process 80 receives an imagedepicting an actual configuration of the fixture. In an example, thetablet computer takes a picture of the actual configuration of thefixture. Process 80 associates (88) metadata for the specifiedconfiguration with the picture (image) taken of the actualconfiguration. As noted, the metadata, in this example, is searchabledata that distinguishes the fixture from at least some other fixtures oflike type, and that enables a user accessing the database in complianceserver to search for, and identify, the image.

Process 80 sends (92) the image, along with the metadata, over a networkto compliance server 32, which is remote from the computing device inthis example, but may be local to the computing device in otherexamples. Compliance server 32 stores the image in its database, alongwith the received, associated, searchable metadata. Computer systems 66to 68 may thereafter search for a fixture by searching the metadata, andretrieve, as a result, an image showing the actual configuration of thefixture at a particular time. In this way, an owner of the fixture mayconfirm that the fixture is a compliant fixture. In a case that thespecified configuration substantially matches the actual configuration,process 80 may send, along with the image and the metadata, a messageindicating that the fixture is in compliance with the specifiedconfiguration. In a case that the specified configuration does notsubstantially match the actual configuration, process 80 may send, toserver 32 a message indicating that the fixture is not in compliancewith the specified configuration.

As noted above, a single button or other control on a UI of computingdevice 46 may be activated to cause the computing device to performmultiple functions automatically (e.g., without further userintervention). That is, code for controlling UI functions may beconfigured so that selecting a single button on the UI triggers thecomputing device to take the image of the actual configuration,associate metadata for the specified configuration with the resultingimage, and send the image and metadata (with a message, if appropriate)to compliance server 32. In other implementations, the process may bemore interactive. For example, the user may hit a “take a picture”button associated with a floorplan graphic, and then hit a “capture aphoto” button in a subsequent UI. The resulting image and metadata maybe transmitted automatically or in response to further interaction withthe UI on the computing device (e.g., hitting a “send” button on theUI).

FIG. 7 is an example of a picture 98 of an actual configuration of afixture, which may be taken by computing device 46 in order to reportcompliance with a manufacturer's requirements. FIG. 8 is an example of afloorplan 100 displayed on the UI of, e.g., computing device 46. As canbe seen, floorplan 100 includes flashing icons 101 to 106 correspondingto fixtures that are present at a location depicted by floorplan 100 andthe require updating or checking. The UI 107 of FIG. 8 includes acontrol 108 instructing the system to take a picture of the actualconfiguration of a fixture. FIG. 9 shows the actual configuration of thefixture 109 displayed on UI 110 (in an example, UI 110 may be arrived atfrom UI 107 of FIG. 8). Control 112 instructs the system to capture apicture of the fixture, to associate metadata with the picture (e.g., anidentity of the promotion for the fixture, a location of the fixture,and the current time and date), and to send that image to a complianceserver.

All or part of the processes described herein and their variousmodifications (hereinafter referred to as “the processes”) can beimplemented, at least in part, via a computer program product, i.e., acomputer program tangibly embodied in one or more information carriers,e.g., in one or more tangible machine-readable storage media, forexecution by, or to control the operation of, data processing apparatus,e.g., a programmable processor, a computer, or multiple computers. Anexample of a computer program used to implement the processes describedherein is an application (or “app”) for a tablet computer, a smartphone,or any other appropriate computing device.

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment. Acomputer program can be deployed to be executed on one computer or onmultiple computers at one site or distributed across multiple sites andinterconnected by a network.

Actions associated with implementing the processes can be performed byone or more programmable processors executing one or more computerprograms to perform the functions of the calibration process. All orpart of the processes can be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) and/or an ASIC(application-specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only storagearea or a random access storage area or both. Elements of a computer(including a server) include one or more processors for executinginstructions and one or more storage area devices for storinginstructions and data. Generally, a computer will also include, or beoperatively coupled to receive data from, or transfer data to, or both,one or more machine-readable storage media, such as mass storage devicesfor storing data, e.g., magnetic, magneto-optical disks, or opticaldisks. Machine-readable storage media suitable for embodying computerprogram instructions and data include all forms of non-volatile storagearea, including by way of example, semiconductor storage area devices,e.g., EPROM, EEPROM, and flash storage area devices; magnetic disks,e.g., internal hard disks or removable disks; magneto-optical disks; andCD-ROM and DVD-ROM disks.

The term “machine-readable storage media” is not meant to encompassnon-statutory subject matter as defined at the time the attached claimsare construed. The term “machine-readable storage media”, however, ismeant to cover any subject matter which is defined as statutory at thetimes the claims are construed.

Each computing device, such as a tablet computer, may include a harddrive for storing data and computer programs, and a processing device(e.g., a microprocessor) and memory (e.g., RAM) for executing computerprograms. Each computing device may include an image capture device,such as a still camera or video camera. The image capture device may bebuilt-in or simply accessible to the computing device.

Each computing device, may include a graphics system, including adisplay screen. A display screen, such as an LCD or a CRT (Cathode RayTube) displays, to a user, images that are generated by the graphicssystem of the computing device. As is well known, display on a computerdisplay (e.g., a monitor) physically transforms the computer display.For example, if the computer display is LCD-based, the orientation ofliquid crystals can be changed by the application of biasing voltages ina physical transformation that is visually apparent to the user. Asanother example, if the computer display is a CRT, the state of afluorescent screen can be changed by the impact of electrons in aphysical transformation that is also visually apparent. Each displayscreen may be touch-sensitive, allowing a user to enter information ontothe display screen via a virtual keyboard. On some computing devices,such as a desktop or smartphone, a physical keyboard and scroll wheelmay be provided for entering information onto the display screen. Eachcomputing device, and computer programs executed thereon, may also beconfigured to accept voice commands, and to perform functions inresponse to such commands. For example, the process described herein maybe initiated at a client, to the extent possible, via voice commands.

Elements of different embodiments described herein may be combined toform other embodiments not specifically set forth above. Elements may beleft out of the processes, computer programs, Web pages, etc. describedherein without adversely affecting their operation. Furthermore, variousseparate elements may be combined into one or more individual elementsto perform the functions described herein. For servers 32 and 40 may bethe same server or part of the same group of servers.

The foregoing implementations describe use of the system in theplacement of cellular telephones and their accessories. However, thesystem described herein may be used to confirm compliance of any productor promotional element within any retail location, or more generally,any appropriate item on any appropriate structure. For example, thesystem may be used to confirm compliance of other types of electronics,clothing, food, shoes, automobile accessories, furniture, toiletries,etc. on retail displays. The system likewise may be used with any typeof retail location, whether generalized, such as Wal-Mart®, orspecialized, such as the cellular telephone outlets described herein.

The systems and techniques described herein may be used in connectionwith the systems and techniques described in U.S. patent applicationSer. No. 12/788,456, filed May 27, 2010, and entitled GENERATING ALAYOUT OF PRODUCTS, the contents of which are hereby incorporated byreference into this patent application as if set forth herein in full.

Other implementations not specifically described herein are also withinthe scope of the following claims.

What is claimed is:
 1. A method comprising: sending by a servercomputing system (server) to a mobile computing device, informationrepresenting a floorplan, the information includes information about afixture corresponding to a specified configuration of items on thefixture; receiving by the server from the mobile computing device,electronic data corresponding to an image of an actual configuration ofthe fixture, the image of the actual configuration is associated withmetadata that distinguishes the fixture in the image of the actualconfiguration from at least some other fixtures of a like fixture type;executing by the server image recognition code that compares the imageof the actual configuration with information derived from the specifiedconfiguration to produce a result determination that indicates whetherthe actual configuration of the fixture is substantially similar to thespecified configuration of the fixture, and compares the metadata of theactual configuration and the determined configuration to determinewhether the actual configuration matches the specified configuration;and storing by the server electronic data corresponding to the image ofthe actual configuration, the metadata, and the result determinationfrom executing the image recognition code.
 2. The method of claim 1wherein the information representing the floorplan includes at least oneicon corresponding to the fixture, the icon has an associated hyperlinkthat when selected renders on a graphics system of the mobile device thespecified configuration of the fixture.
 3. The method of claim 1,further comprising: receiving by the server from a third party systemthat is different from the mobile computing device, a search request forthe actual configuration; searching by the server in response to thesearch request using the metadata to identify an image showing theactual configuration of the fixture; and sending by the server to thethird party system the image of the actual configuration in response tothe search request.
 4. The method of claim 1 further comprising:determining by the server whether there is a match of the specifiedconfiguration to the actual configuration by comparing metadata of theidentified image of the actual configuration to metadata associated withthe specified configuration; and associating metadata for the specifiedconfiguration with the image of the actual configuration, with themetadata being searchable data to enable search of the database incompliance server to search for and identify, the image.
 5. The methodof claim 4 wherein the result determination of substantially similaroccurs when the metadata indicate that items and locations of items inthe specified configuration substantially match within a predefinedpercentage, the actual configuration of items and locations of items inthe image of the actual configuration.
 6. The method of claim 4 whereinthe result determination is not substantially similar when the metadataindicate that items and locations of items in the specifiedconfiguration do not substantially match within a predefined percentage,the actual configuration of items and locations of items in the image ofthe actual configuration.
 7. The method of claim 1 wherein the metadatacomprises data identifying at least one of a type of the fixture, itemson the fixture, and a physical location of the fixture.
 8. The method ofclaim 1, further comprising: receiving by the server a message from themobile computing device, with the message instructing the server to sendthe metadata to a compliance server along with a fixture-specificidentifier; retrieving by the server the metadata; and sending themetadata to the mobile computing device.
 9. The method of claim 8wherein the message received by the server has the fixture-specificidentifier appended to the image; and the method further comprising:associating by the server the image with the metadata using thefixture-specific identifier.
 10. The method of claim 1 wherein the imagerecognition code that executes on the server is configured to recognizethe fixture and the items displayed on the fixture in the actualconfiguration.
 11. A computer program product tangibly stored on one ormore non-transitory machine-readable media, the computer program productincluding instructions executable by one or more processing devices to:send to a mobile computing device information representing a floorplan,the information includes information about a fixture corresponding to aspecified configuration of items on the fixture; receive from the mobilecomputing device, electronic data corresponding to an image of an actualconfiguration of the fixture, the image of the actual configuration isassociated with metadata that distinguishes the fixture in the image ofthe actual configuration from at least some other fixtures of a liketype; execute image recognition code to compare the image of the actualconfiguration with information derived from the specified configurationto produce a result determination based on whether the actualconfiguration of the fixture is substantially similar to the specifiedconfiguration of the fixture, and to compare the metadata of the actualconfiguration and the determined configuration to determine whether theactual configuration matches the specified configuration; and store in anetworked storage system electronic data corresponding to the image ofthe actual configuration, the metadata, and the result determination.12. The computer program product of claim 11 wherein the sentinformation representing the floorplan includes at least one iconcorresponding to the fixture, the icon has an associated hyperlink thatwhen selected, renders on a graphics system of the mobile device thespecified configuration of the fixture.
 13. The computer program productof claim 11 further comprising instructions to: receive from a thirdparty system that is different from the mobile computing device, asearch request; retrieve the actual configuration based at least in parton using the metadata to identify an image showing the actualconfiguration of the fixture; and send to the third party system theretrieved image of the actual configuration in response to the searchrequest.
 14. The computer program product of claim 11 further comprisinginstructions to: determine whether there is a match of the specifiedconfiguration to the actual configuration by comparing metadata of theidentified image of the actual configuration to metadata associated withthe specified configuration; and associate metadata for the specifiedconfiguration with the image of the actual configuration, with themetadata being searchable data to enable search of the database incompliance server to search for and identify, the image.
 15. Thecomputer program product of claim 14 wherein the result determination ofsubstantially similar is when the metadata indicate that items andlocations of items in the specified configuration substantially matchwithin a predefined percentage, the actual configuration of items andlocations of items in the image of the actual configuration.
 16. Thecomputer program product of claim 14 wherein the result determination isnot substantially similar when the metadata indicate that items andlocations of items in the specified configuration do not substantiallymatch within a predefined percentage, the actual configuration of itemsand locations of items in the image of the actual configuration.
 17. Thecomputer program product of claim 16 wherein the metadata comprises dataidentifying at least one of a type of the fixture, items on the fixture,and a location of the fixture.
 18. The computer program product of claim16 further comprising instructions to: receive from the mobile computingdevice a message to send the metadata to a compliance server along witha fixture-specific identifier; and send the metadata and thefixture-specific identifier to the compliance server.
 19. The computerprogram product of claim 18 wherein the message received from the mobilecomputing device has the fixture-specific identifier appended to theimage; and further comprises instructions to: associate the image withthe metadata using the fixture-specific identifier.
 20. The computerprogram product of claim 16 wherein the image recognition code thatexecutes on the server is configured to recognize in the image of theactual configuration, the fixture and the items displayed on thefixture.
 21. A server computer system comprising: one or more computerprocessor devices; memory coupled to the one or more processor devicesconfigurable to store executable computer instructions storage mediaconfigured to store the executable computer instructions that whenexecuted configure the server computing system (server) to: send to amobile computing device information representing a floorplan, theinformation includes information about a fixture corresponding to aspecified configuration of items on the fixture; receive from the mobilecomputing device, electronic data corresponding to an image of an actualconfiguration of the fixture, the image is associated with metadata thatdistinguishes the fixture from at least some other fixtures of a liketype; execute image recognition code to compare the image of the actualconfiguration with information derived from the specified configurationto produce a result determination based on whether the actualconfiguration of the fixture is substantially similar to the specifiedconfiguration of the fixture, and to compare the metadata of the actualconfiguration and the determined configuration to determine whether theactual configuration matches the specified configuration; and store in anetworked storage system electronic data corresponding to the image ofthe actual configuration, the metadata, and the result determination.22. The server of claim 21 wherein the generated informationrepresenting the floorplan includes at least one icon corresponding tothe fixture, the icon has an associated hyperlink that when selected,renders on a graphics system of the mobile device the specifiedconfiguration of the fixture.
 23. The server of claim 21 furthercomprising instructions to configure the server to: receive from a thirdparty system that is different from the mobile computing device, asearch request; retrieve the actual configuration based at least in parton using the metadata to identify an image showing the actualconfiguration of the fixture; and send to the third party system theretrieved image of the actual configuration in response to the searchrequest.
 24. The server of claim 21 further comprising instructions toconfigure the server to: determine whether there is a match of thespecified configuration to the actual configuration by comparingmetadata of the identified image of the actual configuration to metadataassociated with the specified configuration; and associate metadata forthe specified configuration with the image of the actual configuration,with the metadata being searchable data to enable search of the databasein compliance server to search for and identify, the image.
 25. Theserver of claim 24 wherein the result determination of substantiallysimilar is when the metadata indicate that items and locations of itemsin the specified configuration substantially match within a predefinedpercentage, the actual configuration of items and locations of items inthe image of the actual configuration.
 26. The server of claim 24wherein the result determination is not substantially similar when themetadata indicate that items and locations of items in the specifiedconfiguration do not substantially match within a predefined percentagethe actual configuration of items and locations of items in the image ofthe actual configuration.
 27. The server of claim 21 wherein themetadata comprises data identifying at least one of a type of thefixture, items on the fixture, and a location of the fixture.
 28. Theserver of claim 21 further comprising instructions to configure theserver to: receive from the mobile computing device a message to sendthe metadata to a compliance server along with a fixture-specificidentifier; and send the metadata and the fixture-specific identifier tothe compliance server.
 29. The server of claim 28 wherein the messagereceived from the mobile computing device has the fixture-specificidentifier appended to the image; and further comprises instructions to:associate the image with the metadata using the fixture-specificidentifier.
 30. The server of claim 21 wherein the image recognitioncode that executes on the server is configured to recognize in the imageof the actual configuration, the fixture and the items displayed on thefixture.